Calendar not on Wan side available

It's usually a bad idea to expose services directly to the Internet, but that wasn't your question.

In the sidebar of the Server app window, please select the server by name, then select the Access tab. The network access setting for the service should be All Networks if you want the clients to be able to connect from anywhere. The ports on which the service listens are also shown.

If there's no entry for the service in the Custom Access list, the default settings will apply.

Probably you haven't enabled the service for that user.

Chasjazzez wrote:

I think it has something to do with DNS. From the outside (WAN) I can connect with a OS X Server account to my hostname (server.example.com) But when I'm in my local network (where the server is standing) I have to use the local hostname.

Maybe a different topic, but does anybody know how to get your hostname working within it's own local network?

You're looking to implement use what's called split-horizon DNS, and what are called views. This works, but views are past the ability of the local Server.app user interface. But since you're likely not serving public DNS from these servers, you can avoid all that and set up your internal DNS using the same domain and host names, with internal IP addresses. This does mean you will have to track changes across two pools of DNS servers; across your internal DNS servers and the external DNS servers being used by your DNS registrar. FWIW, I generally use a separate domain inside and outside, or a subdomain of a real and registered domain inside. Externally visible names are thus different from internally-visible names, and all mapping takes place either at the firewall and/or in the Sites (Apache Virtual Hosts) configuration inside Server.app. There are details on DNS configuration on OS X Server available around the 'net, too.

Chasjazzez wrote:

Solved!!

On my router I have a setting "LAN DNS" I directed from there.... 🙂

There's unfortunately no single terminology across all the box vendors, so I don't know what that setting does.

In general... Boxes that provide DHCP services should be updated to reference (only) your own DNS server(s) in any DHCP responses they provide, and should not reference any DNS servers off your local network. This assuming a NAT'd network and assuming the box you're referring to as a router is a box that also provides NAT, firewall and DHCP services.

That probably enables the "reflection" of the IP addresses; where any client references to the public IP from the LAN are routed back into the LAN through the NAT.